The intelligent agent cannot view log tracking

[ssssshql]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:)
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.3.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

Some messages in the log can be traced, while others cannot. After clicking, the interface disappears. I found that this situation may only occur when calling through APIs, and it is unlikely to occur on the dify interface. In addition, these messages that cannot be traced have not been called to the tool as I expected (the response is that it is nonsense)

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

[dosubot]

Based on your description and the codebase analysis, Dify's log tracking and tracing features depend on both backend data and tracing provider configuration. If some logs are visible but others are not, and the UI disappears after clicking, this usually points to one of the following:

• The backend did not return log data for certain messages, possibly due to missing or failed trace batches, or a misconfigured tracing provider.
• The tracing configuration (for providers like Langfuse, LangSmith, Weave, etc.) may be incomplete or not operational, causing some traces to be unavailable in the UI. The system checks provider health and configuration before displaying logs, so any issue here can result in missing logs or empty states in the interface (source).
• The frontend TracingPanel and log components render logs based on the data they receive. If the backend returns empty or undefined data, the UI may show nothing or appear to "disappear" (source).

Troubleshooting steps:

1. Check your tracing provider configuration in the Dify admin panel or environment variables. Make sure all required keys and endpoints are set and the provider is reachable.
2. Review the backend logs (from your Docker containers) for errors related to tracing, log retrieval, or provider communication.
3. Confirm that the logs you expect to see actually exist in the database. Some logs may not be created if a workflow run fails early or if there is a batch delivery issue.
4. If you recently changed tracing providers or updated your configuration, restart your containers to ensure all services pick up the new settings.

There are no known open or closed issues in the repository that exactly match this problem, so it appears to be related to operational or configuration factors rather than a systemic bug in Dify 1.3.1. If the problem persists after checking the above, consider reviewing your tracing provider's health and reviewing any recent changes to your Docker or network setup.

To reply, just mention my name @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}